NetApp.com NetApp On the Web NetApp On the Web
[NOW logo]
Monday, February 20, 2006 [home] [alerts] [profile] 
[My NOW][Service and Support][Education and Consulting][Reseller and Partner]  
[Technical Assistance and Documentation][Software Download][My NetApp Products][Product Programs and Solutions]
  Download Software
 -- ToolChest
 -- Release Metrics
 -- Disk Drive Firmware
 -- System Firmware
 -- Release Advisor
 -- Release Comparison
 -- Backup Certification Matrices
 -- Disk Shelf Firmware


[Search]


SnapDrive™ 3.2R1 for Windows® Description Page

Bug Fixes for this Release
 

SnapDrive™ 3.2R1 contains the following important bug fixes:

  • bug 112084: Backup of storage group failed with the message “VDS volume object for the LUN s/n ‘OdCdGYo5bHa7’ has not been found”
  • bug 160012: During LUN connection on SnapMirror destination volume, SnapDrive might have failed with the error message, "Error: ZAPI: An attempt to online LUN '_____' failed on the filer. Error description: No such initiator group exists."
  • bug 172126: LUN creation/connection might have failed with the error message, "Timeout has occurred while waiting for disk arrival notification."
  • bug 182863: After upgrading to an IBM branded Data ONTAP build, SnapDrive can no longer recognize the existing LUNs or create new LUNs
Features of this Release
 

The SnapDrive™ 3.2R1 software introduces support for the following:

  • Multi-Path I/O (MPIO) over iSCSI using the QLogic™ 4010 iSCSI Host Bus Adapter (HBA) (requires the purchase of the MPIO license for Windows)
  • MPIO on iSCSI using the Microsoft® software initiator 2.0
  • Synchronous SnapMirror® integration
  • Storage Area Network (SAN) booting supported on Fibre Channel Protocol (FCP) and iSCSI HBAs that support SAN booting
  • Important bug fixes. See Bug Fixes in the release notes
  • Internationalization for the German language

SnapDrive 3.2R1 recognizes Microsoft Windows Hardware Quality Lab (WHQL) certified iSCSI HBAs. See the iSCSI Host Support Matrix for the most up to date information about HBAs qualified for use with SnapDrive.

Limitations
 

SnapDrive 3.2R1 does not support the following:

  • Management of VLDs and conversion of VLDs to LUNs
  • Use on a 64-bit Windows OS
  • Use of LUN cloning
  • Use of SnapDrive to manage dynamic disks or raw disks
  • Use of qtree quotas (however, SnapDrive does support the use of qtrees without quotas)
  • Automatic trigger of qtree based synchronous mirroring (however, SnapDrive does support the use of SnapMirror to replicate volumes)
  • Connection to Data ONTAP MultiStore® virtual filer partitions (however, SnapDrive can connect directly to the physical “hosting” filer [vfiler0] in a MultiStore installation)
  • Extended partitions in a virtual disk (SnapDrive only supports a single, primary partition on a virtual disk)
  • Use of QLogic iSCSI HBAs for Windows 2000 Microsoft® Cluster Service (MSCS) with or without MPIO

Considerations when using the Microsoft iSCSI software initiator:

  • In a noncluster configuration, the Exchange service and the SQL service must be configured with a dependency on the iSCSI software initiator service.
  • Use of the Microsoft iSCSI software initiator is not supported with the Windows 2000 Microsoft Cluster Service (MSCS).
System Requirements
 

The following table lists the SnapDrive system requirements.

Component Requirement
Operating system on the filer

Data ONTAP software versions 6.5.4 through 7.0.x

Note: For the most current list of supported Data ONTAP software versions, see the SnapManager and SnapDrive Compatibility Matrix.
Licenses enabled on the filer

 

 
  • iSCSI, if you plan to use iSCSI-accessed virtual disks
  • FCP, if you plan to use FCP-accessed virtual disks
  • SnapRestore® software, which is required only for restoring virtual disks from Snapshot™ copies
  • SnapMirror, if you plan to use the SnapMirror option
Note: The iSCSI and FCP licenses supplied with SnapDrive enable all the CIFS functionality necessary for using SnapDrive. If you also want full-featured, direct CIFS access to a particular filer, you must install a separate CIFS license on that filer.
Hardware on the Windows host machine
  • 500 MHz Pentium® III
  • 256 MB system RAM
  • Emulex® LP9002L-F2 or LP10000 HBAs for FCP, supplied by NetApp

Emulex driver:

If you are running SnapDrive 3.2R1 on a Windows 2003 host in an FCP environment, download and install Emulex driver 5-1.11a0 (release notes included in ZIP file).

HBAs and NICs:

To determine the number and type of HBAs and NICs required by each host in your SnapDrive configuration, see the section on selecting a SnapDrive configuration in the SnapDrive 3.2 Installation and Administration Guide.

Obtain the latest firmware and drivers for the HBAs and network interface cards (NICs) you are using, to ensure high network bandwidth and ease of configuration.

  • The NIC you use to facilitate data transfer for the Microsoft iSCSI software initiator can come from any vendor, but must have the appropriate LOGO certification: "Designed for Windows Server 2003" or "Designed for Windows 2000".
  • The latest FCP driver and firmware for Windows 2000 is available on the NOW site . From this gateway, navigate to the SAN (FCP) Host Attach Kit for Windows download page.
  • The Microsoft iSCSI software initiator must be downloaded from the Microsoft site. For directions and links, go to the NOW site, scroll to the iSCSI Host Support Kit item, select the appropriate platform, and then click Go.
  • If you are using QLogic HBAs, see the iSCSI Host Compatibility Matrix for the most up-to-date information about HBAs qualified for use with SnapDrive.

 

Operating system on the Windows host machine

 

 
One of the following operating systems:
  • Windows 2000 Server with Service Pack 4 (SP4)
  • Windows 2000 Advanced Server with SP4 (for Windows-cluster configurations)
  • Windows 2003 Standard Edition with SP1 or Microsoft hotfixes
  • Windows 2003 Enterprise Edition with SP1 or Microsoft hotfixes
  • Windows Server 2003 R2
Microsoft Windows hotfixes Before you can install SnapDrive, your host machine must have the appropriate Microsoft hotfixes installed.
Note: The Microsoft hotfixes 293778, 815198, 833167, 867818, 885294, 886652, 887532, 886800, 891957, 896592, 898790, 902837, and 903081 and must be requested directly from Microsoft Product Support Services at http://support.microsoft.com/.
Note: Specify the directory to which you want to download Microsoft hotfixes 824354 and/or 822831.

For Windows 2003/2003 R2

  • If your host is running Windows 2003 Standard Edition or Enterprise Edition without SP1, you must install hotfixes 833167, 867818, 886652, 887532, 896592, and 903081.
  • If your host is running Windows 2003 Standard Edition or Enterprise Edition with SP1, you must install hotfixes 891957, 898790, 902837, and 903081.
  • If your host is running Windows 2003 Enterprise Edition in a cluster, you must install hotfixes 824354 and 886800.

For Windows 2000

  • If your host is running Windows 2000 Server or Advanced Server with SP4, you must install hotfixes 293778, 815198, 867818, and 885294. Before installing hotfix 293778, see Bug ID 113541 in "Known issues" of the release notes.
Note: Although SP4 includes hotfix 815198, sometimes this hotfix does not update correctly and you are prompted that this hotfix is required. If prompted, install the individual hotfix or re-apply SP4.
Note: If your host is running Windows 2000 and you encounter the problem described in the Microsoft Knowledge Base article 822831, you must install hotfix 822831.
Preinstallation Steps
 

Before you download and install SnapDrive, complete the following steps:

 

  1. Download the iSCSI-protocol license, if you are currently using VLD-type virtual disks. You need this license if you currently have iSCSI LUNS or you intend to create iSCSI LUNs (either from scratch or by converting VLDs).
  2. Download the FCP-protocol license, if you are currently using LUN-type virtual disks. You need this license if you currently have FCP LUNs or you intend to create FCP LUNs (either from scratch or by converting VLDs).
  3. If you are currently running a SnapDrive version earlier than SnapDrive 3.1, you must install at least one of the following licenses at the time you upgrade or install the SnapDrive 3.2R1 software.

    • Download the SnapDrive license for LUN Provisioning and snapshot management. After you click the SnapDrive license link, navigate to the license by choosing the "Show me all" search method, selecting SDR-WIN, then clicking Go.

    • Download the MPIO license for MPIO path management. After you click the MPIO license link, navigate to the license by choosing the "Show me all" search method, selecting SDR-MPIO, then clicking Go.

 

Note: If you are currently running SnapDrive 3.1, skip to Step 4, you already installed one or both of these licenses when you installed SnapDrive 3.1.

 

  1. Download the SnapDrive 3.2 Installation and Administration Guide.

  2. Read Chapter 3, "Installing or Upgrading SnapDrive," in the SnapDrive 3.2 Installation and Administration Guide.

Product Documentation
 

Software documentation

  • To view the Release Notes for this release of SnapDrive, click here.
  • To view the documentation for this release of SnapDrive, click here.
  • To download the documentation, select ZIP file format or TAR file format.
  NOTE: If you are using the Internet Explorer 4.0 or 5.0 browser and are having problems opening any of the Acrobat® files, you might need to upgrade your browser by downloading the latest Internet Explorer Service Pack. You can also right-click the link and select "Save Target as" to download the Acrobat file, or you can use the Netscape Navigator™ browser to view or print the document.
Software Download Instructions

After you confirm that your system meets the SnapDrive requirements and complete the preinstallation steps, proceed with the download by clicking CONTINUE.

 

Part Number: 215-01667-A0


Copyright | Privacy | Scheduled Downtime | Support Services Event Management | Contact Us